System and method for reconnecting a device to a group call

ABSTRACT

A system and method for reestablishing a voice communications session moderated by a group call server between two or more telephony devices. The method is performed by a processor monitoring the communications session. The method comprises: storing one or more data records representing group call information; detecting disconnection of at least one participating telephony device from the group communications session, and determining that the disconnection was not intentionally initiated; accessing the stored call group information data and causing signals to enable reestablishment of participation by the disconnected device to be sent to the disconnected device; and upon receipt by the group call server from the disconnected device of signals representing a request to reconnect the disconnected device, outputting command signals for reestablishing a communications session between the disconnected device and at least one other device participating in the group communications session.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. Non-Provisionalpatent application Ser. No. 13/536,940, titled, “System and Method forReconnecting a Device to a Group Call”, filed Jun. 28, 2012, which is acontinuation application of U.S. Non-Provisional patent application Ser.No. 12/394,377, filed Feb. 27, 2009, now U.S. Pat. No. 8,238,537, bothof which are hereby incorporated herein by reference in theirentireties.

FIELD

The present application relates generally to telecommunications and,more specifically, to a system and method for reconnecting a device to agroup, or conference, call

BACKGROUND

A conference call, sometimes also referred to as a group call, istypically a voice call among two or more participant devices. Such acall is typically moderated by a call moderator, such as asuitably-programmed telephone services server, which can be controlledeither by one of the call participant devices or by an independent partynot controlled by either of the call participant devices, and eachparticipant must be authorized and authenticated by the call controllerin order to join the call. This authorization and authenticationtypically requires the user to enter a passcode or PIN, which maycomprise a lengthy series of numbers or other identifiers.

During a conference call, a device participating in the call may bedisconnected from the group call by hanging up or by the call moderatorending the call with that device. However, in some cases, the device isunintentionally disconnected from the group call, for example when aparticipating wireless communications device enters a tunnel orotherwise loses signal coverage. In order to reconnect a disconnecteddevice to a group call, for example when the device emerges from thetunnel and regains signal coverage, it is generally necessary for thedevice to be re-authorized and re-authenticated by a user of thedisconnected device re-dialing the call-in number and re-entering thelengthy passcode. This may be burdensome for the user and may not beeasily carried out.

It would be desirable to provide a convenient and secure way toreconnect the device to the group or conference call.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made, by way of example, to the accompanyingdrawings which show example embodiments of the present application, andin which:

FIG. 1 shows, in block diagram form, an example system for managingenterprise-related mobile calls, including an enterprise communicationsplatform;

FIG. 2 shows, in block diagram form, further details of an embodiment ofthe enterprise communications platform;

FIG. 3 shows, in block diagram form, another embodiment of theenterprise communications platform;

FIG. 4 shows, in block diagram form, yet another embodiment of theenterprise communications platform;

FIGS. 5A and 5B show, in block diagram form, further details of theenterprise communications platform of FIG. 3; and

FIG. 6 shows, in flow chart form, an embodiment of a method forreconnecting a device to a group call, in accordance with one aspect ofthe disclosure.

Similar reference numerals may have been used in different figures todenote similar components.

DESCRIPTION OF EXAMPLE EMBODIMENTS

In one aspect, the present application provides a method forreestablishing a voice communications session moderated by a group callserver between two or more telephony devices. The method is performed bya processor monitoring the communications session. The method comprises:storing, in a memory accessible by a processor monitoring participationof at least one telephony device in a group communications sessionbetween a plurality of participating telephony devices, one or more datarecords representing group call information, the group call informationincluding information useable for reestablishing participation by the atleast one telephony device in the group call session; detectingdisconnection of the at least one participating telephony device fromthe group communications session, and determining that the disconnectionwas not intentionally initiated; accessing the stored call groupinformation data and, using such accessed data, causing signals adaptedto enable reestablishment of participation by the at least onedisconnected telephony device in the group call session to be sent fromthe group call server to the at least one disconnected telephony device;and upon receipt by the group call server from the at least onedisconnected telephony device of signals representing a request toreconnect the disconnected telephony device with the groupcommunications session, outputting command signals adapted forreestablishing a communications session between the disconnectedparticipating device and at least one other device participating in thegroup communications session.

In another aspect, the present application provides a method in a devicefor reconnecting the device to a group call in an enterprisecommunication network, the network comprising a group call server. Themethod comprises: maintaining, at the device, connection information forthe group call; detecting, at the device, an unintentional disconnect ofthe device from the group call; sending a reconnection request to theserver, the reconnection request containing the connection information;and reconnecting to the group call.

In another aspect, the present application provides a system configuredfor reestablishing a voice communications session moderated by a groupcall server between two or more telephony devices. The system comprisesa processor and a memory accessible by the processor, wherein: thememory comprises one or more data records representing group callinformation, the group call information including information useablefor reestablishing participation by the at least one telephony device inthe group call session. The processor is configured to: detectdisconnection of the at least one participating telephony device fromthe group communications session, and to determine that thedisconnection was not intentionally initiated; access the stored callgroup information data and, using such accessed data, cause signalsadapted to enable reestablishment of participation by the at least onedisconnected telephony device in the group call session to be sent fromthe group call server to the at least one disconnected telephony device;and upon receipt by the group call server from the at least onedisconnected telephony device of signals representing a request toreconnect the disconnected telephony device with the groupcommunications session, output command signals configured to reestablisha communications session between the disconnected participating deviceand at least one other device participating in the group communicationssession.

Other aspects of the present application will be apparent to those ofordinary skill in the art from a review of the following detaileddescription in conjunction with the drawings.

Embodiments of the present application are not limited to any particularoperating system, mobile device architecture, server architecture, orcomputer programming language.

The present application relates to the control and management ofcommunications. Although reference may be made to “calls” in thedescription of example embodiments below, it will be appreciated thatthe described systems and methods are applicable to session-basedcommunications in general and not limited to voice calls. It will alsobe appreciated that the systems and methods may not be limited tosessions and may be applicable to messaging-based communications in someembodiments.

Reference is now made to FIG. 1, which shows, in block diagram form, anexample system, generally designated 10, for the control and managementof communications. The system 10 includes an enterprise or businesssystem 20, which in many embodiments includes a local area network(LAN). In the description below, the enterprise or business system 20may be referred to as an enterprise network 20. It will be appreciatedthat the enterprise network 20 may include more than one network and maybe located in multiple geographic areas in some embodiments.

The enterprise network 20 may be connected, often through a firewall 22,to a wide area network (WAN) 30, such as the Internet. The enterprisenetwork 20 may also be connected to a public switched telephone network(PSTN) 40 via direct inward dialing (DID) trunks or primary rateinterface (PRI) trunks.

The enterprise network 20 may also communicate with a public land mobilenetwork (PLMN) 50, which may also be referred to as a wireless wide areanetwork (WWAN) or, in some cases, a cellular network. The connectionwith the PLMN 50 may be made via a relay 26, as known in the art.

The enterprise network 20 may also provide a wireless local area network(WLAN) 32 a featuring wireless access points. Other WLANs 32 may existoutside the enterprise network 20. For example, WLAN 32 b may beconnected to WAN 30.

The system 10 may include a number of enterprise-associated mobiledevices 11 (only one shown). The mobile devices 11 may include devicesequipped for cellular communication through the PLMN 50, mobile devicesequipped for Wi-Fi communications over one of the WLANs 32, or dual-modedevices capable of both cellular and WLAN communications. WLANs 32 maybe configured in accordance with one of the IEEE 802.11 specifications.

It will be understood that the mobile devices 11 include one or moreradio transceivers and associated processing hardware and software toenable wireless communications with the PLMN 50 and/or one of the WLANs32. In various embodiments, the PLMN 50 and mobile devices 11 may beconfigured to operate in compliance with any one or more of a number ofwireless protocols, including GSM, GPRS, CDMA, EDGE, UMTS, EvDO, HSPA,3GPP, or a variety of others. It will be appreciated that the mobiledevice 11 may roam within the PLMN 50 and across PLMNs, in known manner,as the user moves. In some instances, the dual-mode mobile devices 11and/or the enterprise network 20 are configured to facilitate roamingbetween the PLMN 50 and a WLAN 32, and are thus capable of seamlesslytransferring sessions (such as voice calls) from a connection with thecellular interface of the dual-mode device 11 to the WLAN 32 interfaceof the dual-mode device 11, and vice versa.

The enterprise network 20 typically includes a number of networkedservers, computers, and other devices. For example, the enterprisenetwork 20 may connect one or more desktop or laptop computers 15 (oneshown). The connection may be wired or wireless in some embodiments. Theenterprise network 20 may also connect to one or more digital telephonesets 17 (one shown).

The enterprise network 20 may include one or more mail servers, such asmail server 24, for coordinating the transmission, storage, and receiptof electronic messages for client devices operating within theenterprise network 20. Typical mail servers include the MicrosoftExchange Server™ and the IBM Lotus Domino™ server. Each user within theenterprise typically has at least one user account within the enterprisenetwork 20. Associated with each user account is message addressinformation, such as an e-mail address. Messages addressed to a usermessage address are stored on the enterprise network 20 in the mailserver 24. The messages may be retrieved by the user using a messagingapplication, such as an e-mail client application. The messagingapplication may be operating on a user's computer 15 connected to theenterprise network 20 within the enterprise. In some embodiments, theuser may be permitted to access stored messages using a remote computer,for example at another location via the WAN 30 using a VPN connection.Using the messaging application, the user may also compose and sendmessages addressed to others, within or outside the enterprise network20. The messaging application causes the mail server 24 to send acomposed message to the addressee, often via the WAN 30.

The relay 26 serves to route messages received over the PLMN 50 from themobile device 11 to the corresponding enterprise network 20. The relay26 also pushes messages from the enterprise network 20 to the mobiledevice 11 via the PLMN 50.

The enterprise network 20 also includes an enterprise server 12.Together with the relay 26, the enterprise server 12 functions toredirect or relay incoming e-mail messages addressed to a user's e-mailaddress within the enterprise network 20 to the user's mobile device 11and to relay incoming e-mail messages composed and sent via the mobiledevice 11 out to the intended recipients within the WAN 30 or elsewhere.The enterprise server 12 and relay 26 together facilitate “push” e-mailservice for the mobile device 11 enabling the user to send and receivee-mail messages using the mobile device 11 as though the user wereconnected to an e-mail client within the enterprise network 20 using theuser's enterprise-related e-mail address, for example on computer 15.

As is typical in many enterprises, the enterprise network 20 includes aPrivate Branch eXchange 16 (although in various embodiments the PBX maybe a standard PBX or an IP-PBX, for simplicity the description belowuses the term PBX to refer to both) having a connection with the PSTN 40for routing incoming and outgoing voice calls for the enterprise. ThePBX 16 is connected to the PSTN 40 via DID trunks or PRI trunks, forexample. The PBX 16 may use ISDN signaling protocols for setting up andtearing down circuit-switched connections through the PSTN 40 andrelated signaling and communications. In some embodiments, the PBX 16may be connected to one or more conventional analog telephones 19. ThePBX 16 is also connected to the enterprise network 20 and, through it,to telephone terminal devices, such as digital telephone sets 17,softphones operating on computers 15, etc. Within the enterprise, eachindividual may have an associated extension number, sometimes referredto as a PNP (private numbering plan), or direct dial phone number. Callsoutgoing from the PBX 16 to the PSTN 40 or incoming from the PSTN 40 tothe PBX 16 are typically circuit-switched calls. Within the enterprisere.g. between the PBX 16 and terminal devices, voice calls are oftenpacket-switched calls, for example Voice-over-IP (VoiP) calls.

The enterprise network 20 may further include a Service ManagementPlatform (SMP) 18 for performing some aspects of messaging or sessioncontrol, like call control and advanced call processing features. TheSMP 18 may, in some cases, also perform some media handling.Collectively the SMP 18 and PBX 16 may be referred to as the enterprisecommunications platform, generally designated 14. It will be appreciatedthat the enterprise communications platform 14 and, in particular, theSMP 18, is implemented on one or more servers having suitablecommunications interfaces for connecting to and communicating with thePBX 16 and/or DID/PRI trunks. Although the SMP 18 may be implemented ona stand-alone server, it will be appreciated that it may be implementedinto an existing control agent/server as a logical software component.As will be described below, the SMP 18 may be implemented as amulti-layer platform.

The enterprise communications platform 14 implements the switching toconnect session legs and may provide the conversion between, forexample, a circuit-switched call and a VoiP call, or to connect legs ofother media sessions. In some embodiments, in the context of voice callsthe enterprise communications platform 14 provides a number ofadditional functions including automated attendant, interactive voiceresponse (IVR), call forwarding, voice mail, etc. It may also implementcertain usage restrictions on enterprise users, such as blockinginternational calls or 1-900 calls. In many embodiments, SessionInitiation Protocol (SIP) may be used to set up, manage, and terminatemedia sessions for voice calls. Other protocols may also be employed bythe enterprise communications platform 14, for example, Web Services,Computer Telephony Integration (CTI) protocol, Session InitiationProtocol for Instant Messaging and Presence Leveraging Extensions(SIMPLE), and various custom Application Programming Interfaces (APis),as will be described in greater detail below.

One of the functions of the enterprise communications platform 14 is toextend the features of enterprise telephony to the mobile devices 11.For example, the enterprise communications platform 14 may allow themobile device 11 to perform functions akin to those normally availableon a standard office telephone, such as the digital telephone set 17 oranalog telephone set 15. Example features may include direct extensiondialing, enterprise voice mail, conferencing or other group calls, calltransfer, call park, etc.

Reference is now made to FIGS. 2 to 4, which show example embodiments ofthe enterprise communications system 14. Again, although references aremade below to “calls” or call-centric features it will be appreciatedthat the architectures and systems depicted and described are applicableto session based communications in general and, in some instances, tomessaging-based communications.

FIG. 2 illustrates an embodiment intended for use in a circuit-switchedTDM context. The PBX 16 is coupled to the SMP 18 via PRI connection 60or other suitable digital trunk. In some embodiments, the PRI connection60 may include a first PRI connection, a second PRI connection, and achannel service unit (CSU), wherein the CSU is a mechanism forconnecting computing devices to digital mediums in a manner that allowsfor the retiming and regeneration of incoming signals. It will beappreciated that there may be additional or alternative connectionsbetween the PBX 16 and the SMP 18.

In this embodiment, the SMP 18 assumes control over both call processingand the media itself. This architecture may be referred to as “FirstParty Call Control”. Many of the media handling functions normallyimplemented by the PBX 16 are handled by the SMP 18 in thisarchitecture. Incoming calls addressed to any extension or direct dialnumber within the enterprise, for example, are always first routed tothe SMP 18. Thereafter, a call leg is established from the SMP 18 to thecalled party within the enterprise, and the two legs are bridged.Accordingly, the SMP 18 includes a digital trunk interface 62 and adigital signal processing (DSP) conferencing bridge 64. The DSPconferencing bridge 64 performs the bridging of calls for implementationof various call features, such as conferencing, call transfer, etc. Thedigital trunk interface 62 may be implemented as a plurality oftelephonic cards, e.g. Intel Dialogic cards, interconnected by a bus andoperating under the control of a processor. The digital trunk interface62 may also be partly implemented using a processor module such as, forexample, a Host Media Processing (HMP) processor.

The SMP 18 may include various scripts 66 for managing call processing.The scripts 66 are implemented as software modules, routines, functions,etc., stored in non-volatile memory and executed by the processor of theSMP 18. The scripts 66 may implement call flow logic, business logic,user preferences, call service processes, and various featureapplications.

FIG. 3 shows another embodiment of enterprise communications system 14,in which the PBX 16 performs the functions of terminating and/orbridging media streams, but call control functions are largely handledby the SMP 18. In this embodiment, the SMP 18 may be referred to as acall control server 18. This architecture may be referred to as“Third-Party Call Control”.

The call control server 18 is coupled to the PBX 16, for example throughthe LAN, enabling packet-based communications and, more specifically,IP-based communications. In one embodiment, communications between thePBX 16 and the call control server 18 are carried out in accordance withSIP. In other words, the call control server 18 uses SIP-basedcommunications to manage the set up, tear down, and control of mediahandled by the PBX 16. In one example embodiment, the call controlserver 18 may employ a communications protocol conforming to theECMA-269 or ECMA-323 standards for Computer Supported TelecommunicationsApplications (CSTA).

FIG. 4 shows yet another embodiment of the enterprise communicationssystem 14. This embodiment reflects the adaptation of an existing set ofcall processing scripts to an architecture that relies on third-partycall control, with separate call control and media handling. The SMP 18includes a call processing server 74. The call processing server 74includes the scripts or other programming constructs for performing callhandling functions. The SMP 18 also includes a SIP server 72 and a mediaserver 76. The separate SIP server 72 and media server 76 logicallyseparate the call control from media handling. The SIP server 72interacts with the call processing server 74 using acomputer-implemented communications handling protocol, such as one ofthe ECMA-269 or ECMA-323 standards. These standards prescribe XML basedmessaging for implementing Computer Supported TelecommunicationsApplications (CSTA).

The SIP server 72 interacts with the media server 76 using SIP-basedmedia handling commands. For example, the SIP server 72 and media server76 may communicate using Media Server Markup Language (MSML) as definedin IETF document Saleem A., “Media Server Markup Language”, InternetDraft, draft-saleem-msml-07, Aug. 7, 2008. The media server 76 may beconfigured to perform Host Media Processing (HMP).

Other architectures or configurations for the enterprise communicationssystem 14 will be appreciated by those of ordinary skill in the relevantarts.

Reference is now made to FIGS. 5A and 5B, collectively referred to asFIG. 5, which shows another embodiment of the enterprise communicationssystem 14 with a Third Party Call Control architecture. In thisembodiment, the SMP 18 is a multi-layer platform that includes aprotocol layer 34, a services layer 36 and an application layer 38. Theprotocol layer 34 includes a plurality of interface protocols configuredfor enabling operation of corresponding applications in the applicationlayer 38. The services layer 36 includes a plurality of services thatcan be leveraged by the interface protocols to create richerapplications. Finally, the application layer 38 includes a plurality ofapplications that are exposed out to the communication devices and thatleverage corresponding ones of the services and interface protocols forenabling the applications.

Specifically, the protocol layer 34 preferably includes protocols whichallow media to be controlled separate from data. For example, theprotocol layer 34 can include, among other things, a Session InitiationProtocol or SIP 80, a Web Services protocol 82, an ApplicationProgramming Interface or API 84, a Computer Telephony Integrationprotocol or CTI 86, and a Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions or SIMPLE protocol 88. Itis contemplated that the interface protocols 80-88 are plug-ins that caninterface directly with corresponding servers in the enterprise network20, which will be further described below.

For the purposes of this disclosure, SIP 80 will be utilized, althoughit is appreciated that the system 10 can operate using the abovedisclosed or additional protocols. As known by those of ordinary skillin the art, SIP is the IETF (Internet Engineering Task Force) standardfor multimedia session management, and more specifically is anapplication-layer control protocol for establishing, maintaining,modifying and terminating multimedia sessions between two or moreendpoints. As further known by those of ordinary skill in the art, theSIP protocol 80 includes two interfaces for signaling: SIP-Trunk(hereinafter referred to as “SIP-T”) and SIP-Line (hereinafter referredto as “SIP-L”). Specifically, the SIP-T interface is utilized when theendpoint is a non-specific entity or not registered (i.e., whencommunicating between two network entities). In contrast, the SIP-Linterface is utilized when the endpoint is registered (i.e., whendialing to a specific extension). The specific operation of the system10 utilizing SIP 80 will be described in further detail below.

The SMP 18 also includes a plurality of enablers, among other things, aVoiP enabler 90, a Fixed Mobile Convergence or FMC enabler 92, aconference or group call services enabler 94, a presence enabler 96 andan Instant Messaging or IM enabler 98. Each of the enablers 90-98 areused by corresponding services in the services layer 36 that combine oneor more of the enablers. Each of the applications in the applicationlayer 38 is then combined with one or more of the services to performthe desired application. For example, a phone call service may use theVoiP or PBX enabler, and an emergency response application may use thephone call service, an Instant Messenger service, a video call service,and email service and/or a conference service.

The application layer 38 may include a conference services application63 that, together with the conference services enabler 94, enablesmultiple communication devices (including for example desk telephonesand personal computers) to participate in a conference call through useof a centralized conference server 55. As seen in FIG. 5, the conferenceserver 55 may be provided in the enterprise network 20 and may be incommunication with the conference services enabler 94 through forexample SIP protocol 80, although it is recognized that additionalprotocols that control media separate from data may be appropriate, suchas the Web Services protocol 82 or the CTI protocol 86. As will bedescribed in further detail below, the conference call server 55 may beconfigured for directing media and data streams to and from one or morecommunication devices (i.e., mobile devices 11, telephones 17, andcomputers 15).

Reference is again made to FIG. 1. As discussed above, the PLMN 50 maycommunicate with the relay 26, which in turn communicates with theenterprise network 20 via the enterprise server 12.

Group calls may be made through the PSTN 40 or using a mobile device 11via the PLMN 50 or the WLAN 32 a. In the case of a call made through thePSTN 40, the call may be monitored and otherwise moderated by anautomatic data processor such as a suitably-configured enterprise server12 through the VoiP 90 or FMC 92 components of the SMP 18, or by one ormore processors associated with any one or more of participating devices11, 15, 17, 19. For example, in the case of a call using a mobile device11, the device 11 may send a presence signal at fixed time intervals toa moderating enterprise server 12. The presence signal may serve to letthe enterprise server 12 know that the device 11 is still connected tothe network. When one or more time intervals pass without a presencesignal, the enterprise server 12 can thus detect that the device 11 haslost signal coverage or has stopped participating for other reasons, forexample if the device 11 stops working (e.g., where the battery has runout). As will be understood by those skilled in the relevant arts, oncethey have been made familiar with this disclosure, similar monitoring,moderating, and re-connection processes may be performed by processorsincorporated within any one or more of participating devices 11, 15, 17,19.

The enterprise server 12 or other monitoring or moderating processor isthus able to confirm or otherwise determine the working state of atelephony device 11, 15, 17, 19. During a group call, a participant,such as a mobile telephony device 11, may be disconnected from the groupcall by intentional disconnection (e.g., by a user of the device“hanging up” the device 11, 15, 17, 19); by removal or disconnection bythe moderator; or by disconnection through unavailability of the networkor any component thereof necessary to maintain the group call.

The group call may be monitored and otherwise moderated by a group callserver. In some embodiments, the group call server may be the enterpriseserver 12 or a dedicated application or circuit component thereof.Alternatively, the group call server may be a separate component withinthe enterprise network 20. For simplicity, this disclosure will discussthe embodiment where the group call server is the enterprise server 12.However, it will be immediately understood by those skilled in therelevant arts that the group call server may be a separate component.

A group call typically comprises a sustained voice/media sessionmaintained between two or more participant devices by a moderatordevice, which performs functions such as initiation and termination ofthe various communications sessions which comprise the group call. Eachof the devices may establish a call or session leg to the enterpriseplatform 14, by providing the required connection information (e.g.,dial-in number, authorization passcode and authentication PIN) and thecall legs are joined at the enterprise platform 14 into a group call.

The moderating device and each of the participating devices may performthe various functions described herein by executing scripted programmingfunctions, as for example described herein. For example, the moderatingenterprise server 12 may maintain accessible stored data recordsrepresenting group call information, which may for example includeinformation on the active call legs of the group call and the connectioninformation, such as authorization and/or authentication information,for each call leg. Each device may also share in the group callinformation, thus each device shares in the information about, forexample, the dial-in number for the group call, however each device mayhave restricted access to the connection information, such that it onlyshares in its own connection information, thus maintaining the privacyand security of any authorization or authentication information.

When the moderator device determines, as for example according to asuitably programmed protocol script, that a participant device should bedisconnected from the group call, the moderator device communicatessuitably configured signals representing a disconnect command to thecontrolling enterprise server 12 (e.g., by a user sending an instructingto terminate a certain participant number to the enterprise server 12),the call leg of that participant is disconnected and the group callinformation is updated to note that call leg is no longer active and toremove its associated connection information from the group callinformation. An END OF CALL protocol message may be communicated to thegroup call server and/or the disconnected participant device to confirmthe intentional disconnect.

When a user of a participating device wishes to disconnect the devicefrom the group call, the user may cause the device to disconnect itselfby sending an appropriate communication to the enterprise server 12(e.g., by a user sending an END CALL request through the device 11 tothe enterprise server 12); the call leg of that participant device maythen be disconnected from the group call and the group call informationis updated to note that call leg is no longer active and to remove itsassociated connection information from the group call information. AnEND OF CALL protocol message may be communicated to the group callserver and/or the disconnected participant device to confirm theintentional disconnect. In both cases, the intentional disconnection ofa call leg is preceded by a request for disconnection and may beconfirmed by an END OF CALL indicator.

If a call leg is disconnected without a request for disconnection, e.g.if one of the participating devices ceases to respond to or providerequired or expected communications the enterprise server 12 candetermine that an unintentional disconnection has occurred by, forexample, consulting the stored group call information data set andnoting that the data set does not indicate that the device wasintentionally disconnected (e.g., a corresponding flag may be set to acondition indicating that the device is intended to actively continueparticipating in the call). A reconnection may be attempted, the detailsof which are described below.

Reference is now made to FIG. 6, which is a flowchart showing anembodiment of a general method 600 for reconnecting an unintentionallydisconnected device to a group call.

In the system 10, a user may participate in a group call, for exampleusing a mobile device 11. Typically, when a device 11, 15, 17, 19 joinsa group call, the user is required to enter connection information, suchas an authorization passcode and/or an authentication PIN, andsuitably-configured signals are forwarded to the moderating server orother device 12. The moderating server 12 may compare the providedpasscode and/or pin to previously-established authentication codes and,on confirming that the provided codes are correct, can cause a suitablecommunications session, or ‘connection’, to be established. As describedabove, information relevant to the connection, such as one or moreidentifiers corresponding to the participating device, may be maintainedin a stored data set representing the group call information by theenterprise server 12.

The method 600 can begin at block 602, the point at which aparticipating device 11, 15, 17, 19 has been unintentionallydisconnected from a group call.

At block 604, since the enterprise server 12 did not receive any requestfor disconnecting the device 11, 15, 17, 19 from the group call, thegroup call information maintained by the enterprise server 12 isunchanged. That is, the group call information still notes the call legfor that device 11, 15, 17, 19 as being active and still includes theconnection information for that call leg.

At block 606, the unintentional disconnection of the device 11, 15, 17,19 is detected. This may for example be detected by the enterpriseserver 12 as the absence of a call leg that should be active accordingto the group call information. In some examples, this may be where a“heartbeat” or other timed participation signal is not received. Inother examples, a timed participation signal may not be used, such as ina mobile device where such a signal would affect battery performance.The unintentional disconnection may be detected as the absence of anexpected call leg, according to the group call information, and theabsence of an END OF CALL indicator that would indicate that thedisconnect was intentional. Because the enterprise server 12 is able todistinguish between intentional and unintentional disconnections, areconnection is not attempted where the disconnection is intentional,which minimizes processing demands on the server 12. For example, when auser of a device 11, 15, 17, 19 wishes to terminate participation, theuser can, as described above, cause a suitable call termination commandto be sent to the moderating server 12, on receipt of which, the server12 can cause a suitable flag to be set in the call information data set.Thus, a participant device that intentionally disconnects may beprevented from being burdened with a reconnection attempt from theenterprise server 12, and the user of that participant device 11, 15,17, 19 is not bothered with a request from the enterprise server 12 fora reconnection.

At block 608, the enterprise server 12 attempts to reconnect theunintentionally disconnected device 11, 15, 17, 19 to the group call.This attempt may be carried out directly by the moderating server 12 orby any other suitably configured component of enterprise platform 14.The reconnection attempt may comprise sending an invitation request tothe device 11, 15, 17, 19 to rejoin the group call. For example, server12 or a component associated therewith may cause signals representing asuitably-configured request or command to be sent to the disconnecteddevice 11, 15, 17, 19. Such signals may, for example, cause the device11, 15, 17, 19, to ring, and/or to present on a suitably-configureddisplay information informing a user of the device 11, 15, 17, 19 of theattempt and inviting the user to reconnect by, for example, pressing asuitably-configured “pick up” or other key on the device 11, 15, 17, 19.

In some embodiments, the reconnection invitation may be automaticallyaccepted by the device, without any requiring any input from the user.This may be the case, for example, where the user has preconfigured thedevice to automatically rejoin a group call. Alternatively, thereconnection invitation may trigger an output to the user, for example adialog box, asking the user to choose whether or not to reconnect to thegroup call. The reconnection attempt may only proceed if there is apositive response. The user is not required to enter any details aboutthe group call or any connection information, since this information isalready available to the enterprise server 12 via the retained groupcall information.

At block 610, if the device 11, 15, 17, 19 accepts the invitation,confirmation that the device 11, 15, 17, 19 is authorized to reconnectto the group call is made by the server 12 using the connectioninformation that was maintained in the group call information. There isno need for the device 11, 15, 17, 19 to provide the enterprise server12 with previously-provided passcodes, etc., to confirm authorizationfor reconnection. For example, authentication of the device 11, 15, 17,19 may be carried out by comparing the connection information maintainedin the enterprise server 12 with connection information maintained inthe device 11, 15, 17, 19 or the unique PIN inherently associated withthe device 11, 15, 17, 19. Instead of the PIN associated with the device11, 15, 17, 19, a unique PIN associated with the user may be utilized.The user PIN may be created as part of the setup for a group call, andmay offer greater security as it may be more difficult to be cloned orspoofed.

In some embodiments, the reconnection invitation may be automaticallyaccepted by the device, without any requiring any input from the user.This may be the case, for example, where the user has preconfigured thedevice to automatically rejoin a group call. Alternatively, thereconnection invitation may trigger an output to the user, for example adialog box, asking the user may to choose whether or not to reconnect tothe group call. The reconnection attempt may only proceed if there is apositive response. The user is not required to enter any details aboutthe group call or any connection information, since this information isalready available to the enterprise server 12 via the retained groupcall information.

As will be immediately understood by those skilled in the relevant arts,once they have been made familiar with this disclosure, any suitablerefinements or limitations may be made on process for reestablishinggroup call connections according to the disclosure. For example, priorto initiating a reconnection attempt at 608 in process 600, themoderating server may confirm that other participants in the group callhave not, within a desired time of the detected unintentionaldisconnection, intentionally disconnected; and/or the server 12 mayconfirm that the unintentional disconnection has not occurred longerthan a predetermined elapsed time in the past.

Although the method 600 has been described as being carried out by theenterprise server 12, in some embodiments, the reconnection attempt maybe initiated and executed by the device 11, 15, 17, 19, for examplewhere the enterprise server 12 has given up attempts to reconnect thedevice 11, 15, 17, 19. The steps of the method 600 may be similarlycarried out by the device 11, 15, 17, 19.

At the step 604, the connection information, or a suitable copy of allor a part thereof, may be maintained by the device 11, 15, 17, 19, butthe connection information may be limited to information directlyapplicable to the device 11, 15, 17, 19. For example, the connectioninformation maintained at the device 11, 15, 17, 19 may include onlyauthorization and/or authentication information for that device 11, 15,17, 19 and not other devices in the group call.

At 606, the device 11, 15, 17, 19 may detect an unintentionallydisconnect when, for example, the device 11, 15, 17, 19 has neither sentnor received any END CALL request to the enterprise server 12. Anunintentional disconnect may also be detected by the absence of an ENDOF CALL indicator, which normally indicates an intentional disconnect asexplained above.

At 608, the device 11, 15, 17, 19 attempts to reconnect to the groupcall through the moderating server, or the moderating server 12 attemptsto reconnect the device 11, 15, 17, 19. This step may first requireconfirmation (e.g., via a YES/NO dialog box) from the user that thereconnection should be made. Because the device 11, 15, 17, 19 maintainsthe connection information, this information may be provided to theenterprise server 12 in order to rejoin the group call. The user thusdoes not need to re-enter any connection information, such asauthorization and/or authentication information, or even the call-innumber for the group call. This may be referred to as a “one buttonjoin”, where the user only has to press a single button to indicate aYES response to a dialog box asking whether or not to join a group call,and no other input is required from the user. The device 11, 15, 17, 19may attempt to reconnect automatically without any user input, forexample where the user has preconfigured the device 11, 15, 17, 19 toautomatically reconnect to a group call.

The device 11, 15, 17, 19 may be preconfigured to automatically rejoin agroup call without requiring any confirmation from the user; optionallysuch a setting may be over-ruleable by suitable scripting of theenterprise server 12, for example based on security policies set on theserver.

At 610, the device 11, 15, 17, 19 is reconnected to the group call. Thismay include authorization and/or authentication (or confirmation ofprevious authorization or authentication) of the device 11, 15, 17, 19by the enterprise server 12, for example by comparing the connectioninformation in the group call information maintained at the enterpriseserver 12 with the connection information provided by the device 11, 15,17, 19.

In some embodiments, the enterprise server 12 will attempt to reconnectto a device 111 15, 17, 19 that was unintentionally disconnected foronly a preset period of time, for example 10 minutes, after which nofurther reconnection attempts will be made. This situation may occurwhere the device 11, 15, 17, 19 has roamed into an area with no signalcoverage, for example a tunnel. When the device 11, 15, 17, 19 regainssignal coverage, although there may be no further reconnection attemptsfrom the enterprise server 12, the device 11, 15, 17, 19 retains thegroup call information, and thus may itself attempt to reconnect withthe group call as described above.

In some embodiments, for example where the device 11, 15, 17, 19 isunintentionally disconnected due to loss of signal coverage, theenterprise server 12 will make a reconnection attempt only when theenterprise server 12 detects that the device 11, 15, 17, 19 has regainedsignal coverage. This may be suitable where the device 11, 15, 17, 19 isconfigured to send a presence signal to the enterprise server 12 atfixed time intervals, as discussed above. When one or more timeintervals pass without a presence signal being received at theenterprise server 12, the enterprise server 12 determines that thedevice 11, 15, 17, 19 has lost signal coverage. It may be a waste ofcomputing resources to attempt to reconnect the device 11, 15, 17, 19immediately, since the attempt is sure to fail without signal coverage.Instead, the enterprise server 12 may wait until a presence signal isagain received from the device 11, 15, 17, 19, indicating that thedevice 11, 15, 17, 19 has regained signal coverage. Only after theenterprise server 12 has determined that the device 11, 15, 17, 19 hasregained signal coverage will the enterprise server 12 attempt toreconnect to the device 11, 15, 17, 19.

Although the above description refers to the enterprise server 12 andthe enterprise communication platform 14, in some embodiments, herenetwork topology permits, an unintentionally disconnected call leg maybe reconnected by low level network layers using the shared group callinformation. This may be based on the least cost routing preferencespreset by the system.

Certain adaptations and modifications of the described embodiments canbe made. Therefore, the above discussed embodiments are considered to beillustrative and not restrictive.

What is claimed is:
 1. A method executed by a group call server forreestablishing a voice communication session moderated by the group callserver providing a group communications session between two or moretelephony devices, the method comprising: monitoring, by the group callserver, for a request for disconnection of a voice communication sessionfrom a telephony device of the two or more telephony devices; detecting,by the group call server, a disconnection of the voice communicationsession; in response to detecting that the voice communication sessionhas been disconnected, and that the request for disconnection of thevoice communication session has not been received by the group callserver, sending an invitation to the telephony device to reestablish thevoice communication session; and in response to receiving an acceptanceto the invitation from the telephony device, reestablishing, by thegroup call server, the voice communication session with the telephonydevice, wherein reestablishing the voice communication session comprisesat least one of authorizing and authenticating the telephony deviceusing at least one of authorization information and authenticationinformation.
 2. The method of claim 1, wherein detecting thedisconnection of the voice communication session includes: monitoringfor a presence signal from the telephony device; and determining thatthe voice communication session is disconnected if the presence signalis not received by the group call server.
 3. The method of claim 1further comprising: accessing call information; determining that thevoice communication session is not to be disconnected based on the callinformation; and if the voice communication session is not to bedisconnected, sending the invitation to the telephony device toreestablish the voice communication session.
 4. The method of claim 1,wherein the at least one of authorization information and authenticationinformation is used for establishing the voice communication sessionwith the telephony device, and wherein the voice communication sessionis reestablished without receiving the authorization information or theauthentication information from the telephony device.
 5. A system forreestablishing a voice communication session moderated by the group callserver providing a group communications session between two or moretelephony devices, the system comprising a processor configured to:monitor, by the group call server, for a request for disconnection of avoice communication session from a telephony device of the two or moretelephony devices; detect, by the group call server, a disconnection ofthe voice communication session; in response to a detection that thevoice communication session has been disconnected, and that the requestfor disconnection of the voice communication session has not beenreceived by the group call server, send an invitation to the telephonydevice to reestablish the voice communication session; and in responseto a reception of an acceptance to the invitation from the telephonydevice, reestablish, by the group call server, the voice communicationsession with the telephony device, wherein reestablishing the voicecommunication session comprises at least one of an authorization and anauthentication of the telephony device using at least one ofauthorization information and authentication information.
 6. The systemof claim 5, wherein the detection of a disconnection of the voicecommunication session includes: a monitoring for a presence signal fromthe telephony device; and a determination that the voice communicationsession is disconnected if the presence signal is not received by thegroup call server.
 7. The system of claim 5, wherein the processor isfurther configured to: access call information; determine that the voicecommunication session is not to be disconnected based on the callinformation; and if the voice communication session is not to bedisconnected, send the invitation to the telephony device.
 8. The systemof claim 5 wherein the at least one of authorization information andauthentication information is used to establish the voice communicationsession with the telephony device, and wherein the voice communicationsession is reestablished without receiving the authorization informationor the authentication information from the telephony device.
 9. Anon-transitory computer readable medium that stores a set ofinstructions that are executable by at least one processor of a groupcall server to cause the group call server to perform a method forreestablishing a voice communication session moderated by the group callserver providing a group communications session between two or moretelephony devices, the method comprising: monitoring, by the group callserver, for a request for disconnection of a voice communication sessionfrom a telephony device of the two or more telephony devices; detecting,by the group call server, a disconnection of the voice communicationsession; in response to detecting that the voice communication sessionhas been disconnected, and that the request for disconnection of thevoice communication session has not been received by the group callserver, sending an invitation to the telephony device to reestablish thevoice communication session; and in response to receiving an acceptanceto the invitation from the telephony device, reestablishing, by thegroup call server, the voice communication session with the telephonydevice, wherein reestablishing the voice communication session comprisesat least one of authorizing and authenticating the telephony deviceusing at least one of authorization information and authenticationinformation.
 10. The non-transitory computer readable medium of claim 9,wherein the detecting a disconnection of the voice communication sessionincludes: monitoring for a presence signal from the telephony device;and determining that the voice communication session is disconnected ifthe presence signal is not received by the group call server.
 11. Thenon-transitory computer readable medium of claim 9, wherein the set ofinstructions that are executable by the at least one processor of thegroup call server to cause the group call server to further perform:accessing call information; determining that the voice communicationsession is not to be disconnected based on the call information; and ifthe voice communication session is not to be disconnected, sending theinvitation to the telephony device.
 12. The non-transitory computerreadable medium of claim 9 wherein the at least one of authorizationinformation and authentication information is used for establishing thevoice communication session with the telephony device, and wherein thevoice communication session is reestablished without receiving theauthorization information or the authentication information from thetelephony device.